The operational reality layer

Where we
actually are.

Honest build status · 9-Box pipeline · 7 lanes × 9 domain teams

Parts I + II describe the WHY and the HOW. This view shows the WHAT — how a client actually moves through the 9-Box pipeline, which lanes are acid-tested vs framework-only, and where the 4 Phased Build phases really sit.

v3 calibration. v2 implied four phases in sequence. v3 is honest: P1 done, P2 in flight (5 of 7 active clients lack a Master Strategy doc), P3 is one auto-fix loop in draft mode, P4 is deprioritized.

Phased Build · honest status

Where we actually are — not where v2 hoped

§1.5

9-Box Service Delivery — the canonical pipeline

CRO → SEO → GEO order is non-negotiable

Every service runs through these nine boxes. Boxes 1, 2, 5–9 are universal. Boxes 3 (SEO) and 4 (GEO) are service-conditional — they don't always apply per lane. Box 9 feeds back into Box 1 for the next cycle.

→ lanes

7 service lanes · 9 domain teams

Real slugs · honest status

Real slugs from the codebase — not the L_WEB / L_GBP / L_ADS invention from v2.1. Only the website lane is acid-tested. Domain Teams cross-cut the lanes; UX Design is dormant (Claude Design is the canonical UX surface per Chad 2026-05-26).

Service lanes — by role

Status colors: green = acid-tested · amber = partially shipped · grey = spec or framework only

9 Domain Teams · cross-cut the lanes

UX Design dormant

→ prs

8-Layer Production Readiness Standard

Replaces v2.1's invented R1–R7 ladder

→ chassis

The Enforcement Chassis

Part IV in flight · real frameworks the 73-day window added

Hand v3 to Claude Code

Copy the full constitution as clean markdown — Parts I + II plus chassis, lanes, teams, PRS, and the v2 → v3 delta. The handoff format.

Creative Partner OS · v3.0 · 2026-05-26 · View all directions

Where weactually are.